|
|
Hi Wooshin, Please check https://mantis.cnsbg.foxconn.com/vaas/view.php?id=888#c4354 For BA01, BT funcion is not supported. |
|
|
Hi River, I know about rcd history but skb is requesting to support BA01 at this time. Please support it (BT function of BA01 ). Thanks. |
|
|
Hi Wooshin, Because BA01 is very special RCU and difficult to port it on a new platform based on Eagle project's experience. I think we should go Biz talk between both side first, and then go technical part if there is consensus between us. Thanks~ |
|
|
Hi Jacky Chiang, Could you explain your difficulties ? You have experience with BA01 in Eagle. And you already support BA02 in SWAN. BA01 and BA02 use same Keycode. Could you explain more detail for our understanding ? We just said that you should include BA01 Proudt ID and version No. in your SW. If I have any misunderstanding, please let me know. BR S YOON |
|
|
Hi Mr. Yoon, If you want to support BA01 keycode only, I think it's doable. But, as you know, BA01 RCU support earphone(BT A2DP profile) using UEI chip and our SWAN use Realtek BT chip. There are many compatibility issues between BA01 RCU and Eagle we suffered during initial development and implementation in 2019/2020 and it takes long time to fix them. So I suggest that could you let us know which features of BA01 RCU would you like to support so that we can evaluate if it is achievable and efforts? Hi Kerwin, Please provide your comments or thinking about BA01 supporting effort. Thanks, Jacky |
|
|
Hi jacky and River, If you have difficulties to implement it in short time, please add key codes for BT firstly. And you can use more time to make compatible it. Thanks. |
|
|
Hi Wooshin, First, we need to confirm with you, When you say BT key code, it also include NUGU button and Google Asistant button (to capture audio), is it right? We think even to support BT key code, it will need to pur a lot of effort because: 1.The BT chip for SWAN is RTK, we did not know if there is any compatible issue. 2.SWAN supports BT sink/source mode, To pair BA01, it will need also to pair Audio of BA01. We expect this will cause problem and may need a big change and may affect BT audio routing. |
|
|
1. I already shared it with skb and they did request to implement key code first. 2. I don't know what is different between ba01 audio and normal earphone. Can you explain more detaily ? |
|
|
Hi Mr. River Wong and Mr. Jacky Chiang, Why you repeat your concern about BA01 RCU support ? If you provide any test code, then we will check it. Did you already test it ? It is customer's request, not mine. If you worried about any support for BA01 RCU, then it should be solved. Smart3 of INKEK uses BT module that we recommended as a BT 2nd source before. So what you cannot support BA01 does not make sense. And if you need time, then let me know your target schedule. Best Regrads, SuhYoung YOON |
|
|
Hi Mr. Yoon, As you know, BA01 RCU has BLE and A2DP functions. So there are two phase of RCU pairing operations in Sptek's pairing program, one is for BLE and the other is for A2DP. For BLE function, it is related to key code and voice input for NUGU or Google Assistant button. However, there is another earphone function using A2DP in BA01 RCU, this is our concern and difficulty to support it because SWAN already has A2DP sink and source mode and complicated audio routing scenarios. If we support A2DP of BA01 RCU, it seems BT audio routing scenarios will be a big change. We are afraid that adding it will cause many unexpected issues in field and cause higher VOC trend. If SKB only want to support BT key code, not include A2DP, we can evaluate if it is doable and may need SPtek to support modification of pairing program which remove A2DP pairing in 2nd phase. Thanks, Jacky |
|
|
Hi Mr. Jacky Chiang, Thank you for your explanation. I have question about your concerns. 1. BT SoC difference. You highlighted this issue when we started discussion. Do you still have any concern about it now ? 2. Audio Router scenario complexity. I know what you concern. We are discussing about it with SKB. Currently SKB keep asking to implement it. 3. Support Key code mapping, not A2DP. As you know, BA01 can pair both BLE and A2DP. If we want to support only BLE, then we should change both MW SW and RCU SW. So it is not possible.(Main reason is we cannot change RCU firmware) 4. Can you provide any test firmware for it ? We will check Audio scenarion with it. Best Regards, SuhYoung YOON |
|
|
Hi Mr. Yoon, 1. For different BT SoC, we are still concerned about it. As you know, BA01 RCU is using two chips. One is UEI(for BLE) and the other one is QCM CSR(for A2DP). We don't know if there are many compatibility issues among Realtek, UEI and CSR. As you mentioned, does INTEK smart3 support BA01 RCU now? 4. We are discussing internally. And, could you kindly check with SKB if A2DP issues can be ignored when using BA01 RCU ? Thanks, Jacky |
|
|
Hi Jacky Chiang, 1. Can you check it with INTEK Smart3 that you have ? 2. Could you provide test image first ? We cannot confirm that SKB ignore the A2DP issue from the field. We should test it first and check the severity of issue. Based on the test result, we can start to discuss and show what we may have issues on BA01. Best regards, SuhYoung YOON |
|
|
Hi Mr. Yoon, After checking with our engineer, I think we can provide the test image to you by next Fri. Thanks, Jacky |
|
|
Hi jacky, SKB is waiting long time. Can you give us about test image's schedule ? Thanks |
|
|
Hi Wooshin, I think we can provide you 1st version of test image by next Monday. Thanks, Jacky |
|
|
Hi River, When you work for BA01, interval time should be set 7.5ms not 10ms. Please check linked page for details. BTM_BLE_CONN_INT_MIN_LIMIT = 0x0006(7.5ms) Thanks. |
|
|
Hi Wooshin, May I know BA01 RCU will be shipped with SWAN or SKB just want to use BA01 to test and verify functions during BMT ? Thanks, Jacky |
|
|
Hi Jacky Chiang, There are many RCU model for SKB STBs. And almost all RCU type can use for all SKB STB models. SKB wants to keep this policy for SWAN. There are some Users who use both Eagle and SWAN in their home. In this case, user can use a RCU for both STBs. If users use BA01 for SWAN, then it may issue VoC. I think that SKB doesn't have the plan to ship BA01 for SWAN now. But it depends on SKB's situation. So we cannot confirm that SKB will not ship BA01 for SWAN. Best regards, SuhYoung YOON |
|
|
Hi River, Can you release test firmware in today ? |
|
|
Hi Mr. Wooshin, Here's the test firmware URL: https://drive.google.com/drive/folders/1CCmrSdnIpHmgHe02czSALfyvgDP3gp9V?usp=sharing known issues: 1. BLE is sometimes unpaired 2. when A2DP is still bonded, repair the RCU will not succeed (need unbond it manually in setting) beside the keylayout and model porting, I also did some workaround to make the pair flow smoother (eliminate 2 role-switch-with-bt-restart) please check the attached. WeChat截圖_20220711172434.png (21,329 bytes) |
|
|
for issue 3, It is page timeout when pairing with BRM-audio, usually such problem will need BT-vendor to solve it in BT-fw. I want to pull the FW from Intek-smart3 but however, Intek-smart3 can't pair the BRM-audio either. Could you get latest Intek FW that may support BRM-BA01? |
|
|
Hi Mr. Jim Chen, We checked with SKB. INTEK Smart3 can support BA01 RCU. Could you check it with the latest SW version ? I uploaded the latest version as follows : https://drive.google.com/file/d/1IInGnPn_i7o9oWVe6U-DvHA7GJOxW5oe/view?usp=sharing We don't have INTEK Smart3, so I cannot test it. Best Regards, SuhYoung YOON |
|
|
HI Jim, If s/w version of INTEK BOX, you have to upgrade using share image by Mr Yoon. I have done test BA01 RCU in intek smart3 and result is following. BMM-BA01 : RCU pairing = OK, A2DP = OK BRM-BA01 : RCU pairing = OK, A2DP = OK Thanks. |
|
|
Hi Jim, I got a patch for A2DP connection stability. Please apply below patch and check if there is any improvement. https://jira.skbroadband.com/secure/attachment/203244/203244_20220713_system_bt.patch Thanks. |
|
|
Here's my test result, ignoring BLE fail since we wanna focus on A2DP. intek-smart3 2021 version about 5 times test, all A2DP pair fail. intek-smart3 0708 version total=25, A2DP pair fail=16, ok=9 swan, jim's unclear version total=10, A2DP pair fail=4, A2DP scan fail=3, ok=3 add issue5, BRM BLE disconnected after A2DP paired. |
|
|
test with system-bt.patch, 10 pairs (ignore BLE fail) scan fail=3 pair fail=5 ok=2 |
|
|
Test result is not good. I will inform about result to SKB. |
|
|
Here's the estimated work time currently: x. keylayout and stack timing config (1 day, done 7/7) x. detecting earphone jack event and switch role (2 days, done 7/11) 1. BLE sometimes unpaired by some process (2 weeks, target 7/29) I think this is probably from skb-pairing-app, (caused by sink/src switch and stack restart) However from previous experience, those apps affecting all SKB models so they won't change anything. we need to do some workaround maybe block the unpair in lower layer. 2. when A2DP is still bonded, repair the RCU will not succeed, need unbond it manually in setting (TBD) 3. cannot pair BRM audio (3 weeks, target 8/5) this will depend on the response from RTK. though I didn't see a good result of Intek-smart3, but if we are lucky that Intek already report the issue and RTK is in progress. then we have a chance to get the solution earier. 4. unstable - BLE didn't pair, BLE paired but A2DP didn't pair (TBD) 5. BRM BLE disconnected after A2DP paired. (3 days, target 8/10) after BT-FW changed and the modifications of sink/src role switch, we have to test and ensure the primary functions not affected, such as sink-role, nugu, audio-route, pair-BTN(nugu-request-ctrl) senario. one more week expected. (target 8/17) |
|
|
@Mr Yoon, I still want to try Intek's BT-FW, could you get a userdebug build so that I can pull it out? |
|
|
Hi Jim, You can find user-debug image for intek smart3. http://altserver01.duckdns.org/release_by_ALT/usb_bid-at200/ Thanks. |
|
|
intek-smart3 0713 userdebug build total=10, A2DP pair fail=4, ok=6 detail test result: B=BLE, A=A2DP, 11=pair fail, 33=scan fail B33, ok, A11, ok, A11, ok, ok, A11, A11, ok, ok |
|
|
Hi Jim, Do you have any update ? And check "Connection Parameter Update" issue on below link. https://mantis.cnsbg.foxconn.com/vaas/view.php?id=1434 thanks. |
|
|
interval=10 is already applied, it is not related to this, but still thanks for the sharing. after I changed my DUT to latest HW, the pair issue seems to be OK. I'm sorry, but that's still a good news we don't need change bt-fw. the bad news is a2dp sink/src switch is totally in a mess. in app layer, I tried a lot moving the switch point but non success. I'm still working on it and will try list the problems |
|
|
Hi, here's rcu8 test image: https://drive.google.com/drive/folders/1kPARV7jPW6qZ1ApJiCU_s91BEE-3Fvek?usp=sharing please 1. disable com.skb.btv.bluetooth ==> chmod 000 /system/app/btvbtservices && killall com.skb.btv.bluetooth 2. pair it manually with setting, here's a sample video: https://drive.google.com/file/d/11Oz4Qs4z6v8BCyMgJqOabyvDCV_obuEe/view?usp=sharing 3. suggest to use BMM, it is easier to succeed than BRM. |
|
|
Hi Jim, What do I test using this s/w ? Connection stability ? Thanks. |
|
|
Hi Mr. Wooshin, It is for you to know the pair status between SWAN and BA01. It work well without btvbtservices. Everytime A2DP sink/role siwtch (stack restart), the bond state of BLE goes from 12->11, then btvbtservices starts the pairing work, and failed to pair the A2DP in the end. finally remove BLE bond. |
|
|
Hi Jim, What you mean it is working well with BLE connection. Is it right ? But I can't remove btvbtservices. Do you want to remove connect try of btvbtservices ? Thanks. |
|
|
Hi Mr. Wooshin, here's rcu11 test image, it is the 1st ver. that do A2DP-role-switch without bt-stack-restart https://drive.google.com/drive/folders/1-GjzpTKV_-woCS7V7FHhjE7MGor-vcm1?usp=sharing here's know issue: 1. sometimes switch to sink fail. (mobile can't connect) 2. unpair BLE cause bt-stack-restart 3. some other condition cause bt-stack-restart (which leed to btvbtservice unbond BLE) 4. insert earphone to a non-paired-RCU, the RCU bonded and the original one removed (maybe it's a designed feature, should verify with smart3) though this not stable yet, but it should be able to do full BMM/BRM BA01 pair test with normal way (hold # *) |
|
|
1. sometimes switch to sink fail. (mobile can't connect) this happen on my KIDsREAD bt-spk, but not on my Sharp AN-SS1. add some delay during role-switch makes it better, about from 90% fail to 10% (included in rcu11 FW) not yet found the root cause 2. unpair BLE cause bt-stack-restart setProfileServiceState() calls onBluetoothReady(), which reinitialize some global values. and then cause invalid state exception so, remove onBluetoothReady from setProfileServiceState (profile start), move it after setAllProfileServiceStates (bt start). (not included in rcu11 FW) |
|
|
rcu12: https://drive.google.com/drive/folders/1F1dCjDpE7TSWJcY8cnggFkAy3rbHmG4i?usp=sharing 1. fix known issue2 2. sync to v19.534.21 now focus on issue1 |
|
|
Hi Jim, Thanks for your effort. Let me check it also. Thanks. |
|
|
Hi Jim, Are you working for issue1 "sometimes switch to sink fail. (mobile can't connect)" ? Currently, is there any issue in role with without bt stack restart ? Thanks. |
|
|
rcu13: https://drive.google.com/drive/folders/1drb8wCOtIAs3VVsiucd5GLRVzZx5iOBH?usp=sharing known issue 1. sometimes switch to sink fail. (fixed in rcu13) 2. unpair BLE cause bt-stack-restart (fixed in rcu12) 3. some other condition cause bt-stack-restart (which leed to btvbtservice unbond BLE) 4. insert earphone to a non-paired-RCU, the RCU bonded and the original one removed (ignore) 5. when mobile is connected, BA01 can't pair. (new) 6. when A2DP is bonded, repair the RCU will fail (7/13) |
|
|
rcu14: https://drive.google.com/drive/folders/1o2SyVriEEQLm4f3iO10e24VWTN6XV23J?usp=sharing - fix known issue5, 6 - sync to v19.534.23 known issue //1. sometimes switch to sink fail. (fixed in rcu13) //2. unpair BLE cause bt-stack-restart (fixed in rcu12) 3. some other condition cause bt-stack-restart (which leed to btvbtservice unbond BLE) //4. insert earphone to a non-paired-RCU, the RCU bonded and the original one removed (ignore) //5. when mobile is connected, BA01 can't pair. (fixed in rcu14) //6. when A2DP is bonded, repair the RCU will fail (fixed in rcu14) |
|
|
Hi Mr. Yoon, role-switch is a foundamental function so changing it will affect a lot. for example the audio routing, the sink/src device connect behavior, the frontend-bt-btn and nugu-request event... Besides the bugs I found (and I'm focus on fixing them), I believe there will be more bugs not found yet. We need full test to find all the bugs caused by new-role-switch and fix it. However the only feedback I got is the different behavior between BMM and BRM. we don't suggest to add BA01 support in Friday build, it will impact the BMT. |
|
|
Hi Mr. Jim Chen, Mr. River Wong and Mr. Jacky Chiang, We asked you to support this feature a month ago. I think you answered some feedback with some difficulty. I think one month is not short period to implement this function. We understand this changes may impact to the connection with other devices. But SKB keep asking to implement BA01. What is your plan ? Do you think this request is impossible to support ? Our competitors, INTEK and Innopia, are support with their AI2 STB. What is the differences between you and them ? Please share your implementation plan ASAP. How long do you need to support it ? Best regards, SuhYoung YOON |
|
|
rcu15: https://drive.google.com/drive/folders/1Ufayu_jMzkdcXbbfk_b0Dvh9klaEyVgq?usp=sharing //1. sometimes switch to sink fail. (fixed in rcu13) //2. unpair BLE cause bt-stack-restart (fixed in rcu12) 3. some other condition cause bt-stack-restart (which leed to btvbtservice unbond BLE) //4. insert earphone to a non-paired-RCU, the RCU bonded and the original one removed (ignore) //5. when mobile is connected, BA01 can't pair. (fixed in rcu14) //6. when A2DP is bonded, repair the RCU will fail (fixed in rcu14) //7. some BT-SPK (BV300S) connect fail (fixed in rcu15) //8. invalid ACTION_RCU_PAIRING_START when earphone inserted (bug of rcu14, fixed in rcu15) |
|
|
rcu15(=rcu14+a2dpd131) has passed my a2dpd regression test https://docs.google.com/spreadsheets/d/11Mtvn3gx_GB3_Sbj_Ep-Q9A4dxwta845ebVT9HXBxUM/edit?usp=sharing src/sink role switch with KIDsREAD and BMM-Audio over 30 times ok again this is a foundamental function change so we need ALT to test it and feedback. I can't guarantee there's no bug. |
|
|
Hi Jim, We will test it and share result. thanks. |
|
|
Hi Jim, I have done test for Audio routing. Role-switch is related closely with audio routing. There is no issue. Please check below link. https://docs.google.com/spreadsheets/d/1nPiuVKMs_0e9Ez2uPAt4obq8KocPfh9vXX1trCpG4sw/edit#gid=188690815 Thanks. |
|
|
Hi Mr. Wooshin, thanks for the feedback, I'll push BA01 commits with [BTVSBOX-615], here's the list FYI. we add a property to do a2dp-role-switch with original way (restart bt stack, for test only, default is no-rstart) persist.vendor.vasott.roleswitchmethod=restart132 project: device/synaptics/sequoia 2022-08-23 10:48:12 +0800 | jim.jm.chen@fii-fo.. | 2457315 | [BTVSBOX-615] bdroid_buildcfg follow BID 2022-08-23 10:48:09 +0800 | jim.jm.chen@fii-fo.. | 0404f76 | [BTVSBOX-615] sync RCU support from smart3 [1/4] project: frameworks/base 2022-08-23 10:47:30 +0800 | jim.jm.chen@fii-fo.. | 11182831535 | [BTVSBOX-615] add protected broadcast 2022-08-23 10:47:27 +0800 | jim.jm.chen@fii-fo.. | cdf2437a778 | [BTVSBOX-615] broadcast FUNC10 and FUNC16 event project: hardware/realtek 2022-08-23 10:36:49 +0800 | jim.jm.chen@fii-fo.. | 7c3af09 | [BTVSBOX-615] sync RCU support from smart3 [2/4] project: packages/apps/Bluetooth 2022-08-23 10:37:19 +0800 | jim.jm.chen@fii-fo.. | 94366d501 | [BTVSBOX-615] move onBluetoothReady to prevent values reinitialized on role-switch 2022-08-23 10:37:16 +0800 | jim.jm.chen@fii-fo.. | 8e60e1e27 | [BTVSBOX-615] role switch without restart-stack project: syna-release/linux_4_9_q 2022-08-23 10:37:51 +0800 | jim.jm.chen@fii-fo.. | c5dd0bfd | [BTVSBOX-615] sync RCU support from smart3 [3/4] project: system/bt 2022-08-23 10:38:21 +0800 | jim.jm.chen@fii-fo.. | b4736b6f7 | [BTVSBOX-615] fix a2dp switch to sink sometimes fail 2022-08-23 10:38:18 +0800 | jim.jm.chen@fii-fo.. | fbaddaa42 | [BTVSBOX-615] SKB RCU custom interop project: vendor/foxconn 2022-08-23 10:39:21 +0800 | jim.jm.chen@fii-fo.. | 1b96bf6 | [BTVSBOX-615] A2dpDeviceService v1.3.2 2022-08-23 10:39:18 +0800 | jim.jm.chen@fii-fo.. | 69201be | [BTVSBOX-615] A2dpDeviceService v1.3.1 2022-08-23 10:39:16 +0800 | jim.jm.chen@fii-fo.. | c56b83a | [BTVSBOX-615] A2dpDeviceService v1.3.0 2022-08-23 10:39:12 +0800 | jim.jm.chen@fii-fo.. | 9a7dc18 | [BTVSBOX-615] A2dpDeviceService v1.2.9 2022-08-23 10:39:08 +0800 | jim.jm.chen@fii-fo.. | d3cb149 | [BTVSBOX-615] sync RCU support from smart3 [4/4] |
- yk.jung ( (ALTech) Younkwang Jung ) developer
